book: add section about private testnet testing #8937
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
C-trivial
Co-authored-by: Pili Guerra <[email protected]>
arya2
approved these changes
Oct 15, 2024
Comment on lines
+3
to
+5
| The objective of a private testnet test is to test testnet activation in an | ||
| isolated fashion, before the actual testnet activation. It is usually | ||
| done using the current state of the existing testnet. For NU6, it was done |
There was a problem hiding this comment.
Optional/Nitpick:
Suggested change
| The objective of a private testnet test is to test testnet activation in an | |
| isolated fashion, before the actual testnet activation. It is usually | |
| done using the current state of the existing testnet. For NU6, it was done | |
| The objective of a private Testnet test is to test Testnet activation of an upcoming | |
| network upgrade in an isolated fashion, before the actual Testnet activation. | |
| It is usually done using the current state of the existing Testnet. For NU6, it was done |
Comment on lines
+12
to
+13
| Make a backup of your current testnet state. Rename/copy the `testnet` folder to | ||
| `unknowntest` (because that is the name used by Zebra for custom testnets). |
There was a problem hiding this comment.
Optional/Nitpick:
Suggested change
| Make a backup of your current testnet state. Rename/copy the `testnet` folder to | |
| `unknowntest` (because that is the name used by Zebra for custom testnets). | |
| Make a backup of your current Testnet state. Rename/copy the `testnet` folder in | |
| Zebra's state cache directory to the lowercase version of the configured network name, | |
| or the default `unknowntestnet` if no network name is explicitly configured. |
| ### Set Up Lightwalletd Server | ||
|
|
||
| It's a good idea to set up a lightwalletd server connected to your node, and | ||
| have a (testnet) wallet connected to your lightwalletd server. |
There was a problem hiding this comment.
Great point!
Optional/Nitpick:
Suggested change
| have a (testnet) wallet connected to your lightwalletd server. | |
| have a (Testnet) wallet connected to your lightwalletd server. |
|
|
||
| ### Ensure the Activation Height is Set in Code | ||
|
|
||
| While Zebra allows creating a private testnet in the config file, the height is |
There was a problem hiding this comment.
This is a good note, I think we forgot to do this in our first attempt and had to set a new activation height. We may want to offer creating a new branch as an example of how to modify Zebra's relevant dependencies, though it does seem like the best way (alternatives could be to use a path or make modifications in the local Cargo registry then use cargo build --offline).
Optional/Nitpick:
Suggested change
| While Zebra allows creating a private testnet in the config file, the height is | |
| While Zebra allows creating a private Testnet in the config file, the height is |
| [mining] | ||
| debug_like_zcashd = true | ||
| miner_address = "t27eWDgjFYJGVXmzrXeVjnb5J3uXDM9xH9v" | ||
| # if you want to enable mining |
There was a problem hiding this comment.
Suggested change
| # if you want to enable mining | |
| # if you want to enable mining, which also requires selecting the `internal-miner` compilation feature |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
We want to document how to do a private testnet testing, so that we can more easily make another one in the future when required.
Specifications & References
Solution
Tests
Follow-up Work
PR Author's Checklist
PR Reviewer's Checklist